fix(release) use Node 24 and empty NODE_AUTH_TOKEN for OIDC publishing#24
Merged
fix(release) use Node 24 and empty NODE_AUTH_TOKEN for OIDC publishing#24
Conversation
Node 24 ships with npm 11.x which includes OIDC trusted publishing. Set NODE_AUTH_TOKEN to empty string so the .npmrc template does not interfere with the OIDC token exchange at publish time. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Switches the release workflow from Node 22 to Node 24 and sets
NODE_AUTH_TOKENto an empty string in the release step.Why
npm OIDC trusted publishing requires npm >= 11.5.0. Node 22 ships with npm 10.x, while Node 24 ships with npm 11.x which has OIDC support built in. The empty
NODE_AUTH_TOKENprevents the.npmrctemplate (created bysetup-nodewithregistry-url) from interfering with the OIDC token exchange that happens duringnpm publish --provenance.Risk Assessment
Low risk. Node 24 is already tested in CI. The release workflow only runs on manual dispatch.
References